Improve markdown files and add markdownlint#138
Conversation
360b26d to
2f722c0
Compare
2f722c0 to
e1a9825
Compare
Start each file with a h1-level heading, and increment levels for section headings one at a time. These correspond to rules MD041 and MD001 of markdownlint, respectively.
e1a9825 to
d8dd918
Compare
Xymph
left a comment
There was a problem hiding this comment.
Good improvements, with some nice touches like the text type for the Array example.
One more tweak: https://github.com/hamstar/Wikimate/blame/503625f9e2c23a442d8bda368c4974281c2bd1f3/GOVERNANCE.md#L46
Change "the README" into "README.md"
|
General question: how did you add the remarks below the commit message, e.g. "Use dashes for lists..." ? |
- Add introductory context - Reword the introductory paragraphs of GOVERNANCE.md into a proper section - Fix a typo in CONTRIBUTING.md - Apply various fixes recommended by markdownlint
Use dashes for lists, and leave asterisks for emphasis.
d8dd918 to
6dd37f2
Compare
Done :)
A git commit message can have a summary and a body, though most of the time only the former is used, which leads to the conflation of the expression "commit message" with the summary alone. But, as I alluded to recently, there is a recommended maximum length for the summary, so in many cases it's useful to provide additional details in the body. In practice, the way you add content to the commit message body is by making a multi-line commit message, with a blank line separating the summary and the body. In the command line, simply typing enter before closing the quotes will allow you to add additional lines to the string: $ git commit -m "Lorem ipsum↵
> ↵
> Dolor sit amet, consectitur adipisci elit."↵GitHub will display commit message bodies as expandable notes with the "..." sign, as you see above. |
|
And that's another wrap. 👍 |
Uh oh!
There was an error while loading. Please reload this page.